zfsbootmenu: remove legacy root= usage/design #496
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ZFSBootMenu has danced around
$root
for a few years now, as a holdover from very early design decisions picked up from Dracut. We don't actually need to tie ourselves to that variable - and in fact, a lot of the early startup process can be simplified by no longer trying to stuff so much logic into it.To that end, the legacy but undocumented support for
root=zfsbootmenu:POOL=pool
has been completely removed.root
on the ZBM KCL is no longer honored.zbm.prefer
with the documented syntax is now the only way to tell ZFSBootMenu which pool should be preferentially used in the boot process. Accordingly, the globalzbm_prefer_pool
variable is now set when a pool should be preferred, and the accompanyingzbm_require_pool
variable is used to indicate how firm that pool requirement is. One quirk of this is that a pool name ofzfsbootmenu
can now actually be a value thatzbm.prefer
will respect/honor.